You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing training@inductiveautomation.com.
Version:
LESSON LIST
-
4:38Parameters
-
3:35Basic SQL Query
-
3:13SQL Query
-
1:20Named Queries in Reports
-
2:23Tag Historian Query
-
2:06Tag Calculation Query
-
2:29Alarm Journal Query
-
1:27Static CSV
-
5:42Scripting Data Source
-
4:10Nested Queries
Take Topic Challenge
LESSON
Tag Historian Query
Description
Easily access tag history for use in your reports with the Tag Historian Query data source
Video recorded using: Ignition 8.1
Transcript
(open in window)[00:00] In this lesson, I'll show you how to pull tag historian data into your report via the tag historian query data source. To get started, you can create a new data source and select Tag Historian Query. The list of available historical tags will be listed in this window on the left. I have some historical tags measuring tank values. I'll expand historical providers and I can drag and drop my tags into the selected historical tags window. This will auto-populate the Tag Path column and the Data Key Alias. If I were to change the Data Key Alias to something like 'my tag data' that's what I would look for in the key browser. The properties on the right side of the screen allow you to change the data key for the data source, modify the query type, limit the number of rows when in the Preview tab, and configure a nested query system. Towards the bottom, you'll see the properties that allow you to configure the tag history request.
[01:03] I won't go into each individual property in this video. But, this functions the same as a tag history binding in vision. If you'd like to see more info on these properties, you can refer to that page in the user manual. For this query, I'll set it up so that it pulls the latest value from these tags. The way this differs from a tag history binding is when using indirection. My tanks are specified by their tank numbers. So I have a report parameter to help point to the tank I'd like to pull data on. My default value for this parameter is one. To use my parameter in the Tag Path, I'll remove the number and insert my parameter name with curly braces. If I head over to the Design tab, we can take a look at the report layout. I have a table configured to display data from the tag history data source. And the columns are listing my tag values in timestamps. To see this in action, I'll head over to a Report Viewer component in my vision window.
[02:04] You can see the report pulling in data here and if I change the tank number, I get data on the other tank. As you can see, adding tag history data to your report is very easy, and you can also configure indirection for greater flexibility.